Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9bd138aed87117935a8fb07cc84415996e7131021a46e6b917ea9cead33b363

Tx prefix hash: b036a908ed56c2fc8923e1a790ac0143ba80d392480d5af87e58e7430f369a62
Tx public key: 1cfa752e6415dd5bf3d7b8e73eb1d501c2b8e8a80d61f8e76684f2c13fa44759
Timestamp: 1749700007 Timestamp [UCT]: 2025-06-12 03:46:47 Age [y:d:h:m:s]: 00:150:15:07:40
Block: 1303193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105362 RingCT/type: yes/0
Extra: 011cfa752e6415dd5bf3d7b8e73eb1d501c2b8e8a80d61f8e76684f2c13fa4475902110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53d11fd64456d322ba23784705fe7d91b8d4ddfbb32cddfa8dfc10e23a53ce99 0.600000000000 1790770 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": 1303203, "vin": [ { "gen": { "height": 1303193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53d11fd64456d322ba23784705fe7d91b8d4ddfbb32cddfa8dfc10e23a53ce99" } } ], "extra": [ 1, 28, 250, 117, 46, 100, 21, 221, 91, 243, 215, 184, 231, 62, 177, 213, 1, 194, 184, 232, 168, 13, 97, 248, 231, 102, 132, 242, 193, 63, 164, 71, 89, 2, 17, 0, 0, 0, 2, 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