Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4347b780ba89132e93ea3bc4214f6574f8eb78581d932eafd4295bbcc5f25552

Tx prefix hash: bd1465fe5a080ec3df77e369a3b3d06db3469481ad8aba5b8bcbe724e611df5b
Tx public key: b4cd5f573435704053b52bc816049702cff63607fa691f51d7b6dc3af7a52aa0
Timestamp: 1746624510 Timestamp [UCT]: 2025-05-07 13:28:30 Age [y:d:h:m:s]: 00:190:10:29:45
Block: 1277762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133815 RingCT/type: yes/0
Extra: 01b4cd5f573435704053b52bc816049702cff63607fa691f51d7b6dc3af7a52aa00211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4fbff441f7367c241dcc6c5277f9e4476eac34ec4164ea541a39afd2654d58f 0.600000000000 1765119 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": 1277772, "vin": [ { "gen": { "height": 1277762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4fbff441f7367c241dcc6c5277f9e4476eac34ec4164ea541a39afd2654d58f" } } ], "extra": [ 1, 180, 205, 95, 87, 52, 53, 112, 64, 83, 181, 43, 200, 22, 4, 151, 2, 207, 246, 54, 7, 250, 105, 31, 81, 215, 182, 220, 58, 247, 165, 42, 160, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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