Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd24b52b897b8d6ea792cf76039fefdcdeb2e05f291dc66b42e4ba172cc65fc2

Tx prefix hash: f9f6cc782133671b240d9d6c0e04f74db30237a2741b3cd513072ad7180ce671
Tx public key: 44f81a7033813ea011fb7bbd8d12b924d45a6dd271130e1dfef419b024d06c9f
Timestamp: 1755860747 Timestamp [UCT]: 2025-08-22 11:05:47 Age [y:d:h:m:s]: 00:096:04:23:53
Block: 1351937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68692 RingCT/type: yes/0
Extra: 0144f81a7033813ea011fb7bbd8d12b924d45a6dd271130e1dfef419b024d06c9f0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dffc67a7f29797b25456af7f96d6c29dcfb0e56e150413df50000b0f5c097c4 0.600000000000 1839898 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": 1351947, "vin": [ { "gen": { "height": 1351937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dffc67a7f29797b25456af7f96d6c29dcfb0e56e150413df50000b0f5c097c4" } } ], "extra": [ 1, 68, 248, 26, 112, 51, 129, 62, 160, 17, 251, 123, 189, 141, 18, 185, 36, 212, 90, 109, 210, 113, 19, 14, 29, 254, 244, 25, 176, 36, 208, 108, 159, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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