Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 674bf4268ae1edcf218bd6b56b33e23a02d2f29460a045d5ba84f850a02e2930

Tx prefix hash: 8ce3c561694ec97b8dcb734066e6810427ddb8fae6bc879ff6ffa92d54e6034c
Tx public key: 9c28a65b6add3db215ae9df270fe22b4e470a46fe712206d40d92a7e01bad607
Timestamp: 1749650997 Timestamp [UCT]: 2025-06-11 14:09:57 Age [y:d:h:m:s]: 00:153:21:00:49
Block: 1302805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107668 RingCT/type: yes/0
Extra: 019c28a65b6add3db215ae9df270fe22b4e470a46fe712206d40d92a7e01bad60702110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248093818d6eadb872a6724e6b13d63f4867a97144b4ade2c9229accd404a9d8 0.600000000000 1790378 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": 1302815, "vin": [ { "gen": { "height": 1302805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248093818d6eadb872a6724e6b13d63f4867a97144b4ade2c9229accd404a9d8" } } ], "extra": [ 1, 156, 40, 166, 91, 106, 221, 61, 178, 21, 174, 157, 242, 112, 254, 34, 180, 228, 112, 164, 111, 231, 18, 32, 109, 64, 217, 42, 126, 1, 186, 214, 7, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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