Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2a8763f8e44554ff1dbc876d0ea3c2a12d071334ec2fc11737f3531248992bb1

Tx prefix hash: 82301c4720dff59b1e36d4a4c58c15600bc2a6e1365104bfa82ed1f5be8b5387
Tx public key: fdc7f7b0d686b30364fa3d1c5b58b7473dc33572050c7779618b43af158ce8e6
Timestamp: 1763165770 Timestamp [UCT]: 2025-11-15 00:16:10 Age [y:d:h:m:s]: 00:042:13:13:30
Block: 1412295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30464 RingCT/type: yes/0
Extra: 01fdc7f7b0d686b30364fa3d1c5b58b7473dc33572050c7779618b43af158ce8e6021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9d7986a9e1a2d00f5451a632405e1b1a6b476838324333dcef45849305825c5 0.600000000000 1900762 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1412305, "vin": [ { "gen": { "height": 1412295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9d7986a9e1a2d00f5451a632405e1b1a6b476838324333dcef45849305825c5" } } ], "extra": [ 1, 253, 199, 247, 176, 214, 134, 179, 3, 100, 250, 61, 28, 91, 88, 183, 71, 61, 195, 53, 114, 5, 12, 119, 121, 97, 139, 67, 175, 21, 140, 232, 230, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8