Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75452aaf4297c5007193fe7f3b21b0fa9dddf26e520b471193a4858782dc9368

Tx prefix hash: 9614d156e341bfc67be91e2b63b36c7795aa59c1e27ab83a32f1bf7e7fb25ad5
Tx public key: 23b855a5b125d1a1b1e0664253163c9cf54e147807a867a9dd138c3e08adeffb
Timestamp: 1744765034 Timestamp [UCT]: 2025-04-16 00:57:14 Age [y:d:h:m:s]: 00:050:02:49:03
Block: 1262363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35862 RingCT/type: yes/0
Extra: 0123b855a5b125d1a1b1e0664253163c9cf54e147807a867a9dd138c3e08adeffb0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64c37c96a01e4b90325e8dc4bb2c480a21f984201b053d8976735ae2e7a1caa 0.600000000000 1749542 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": 1262373, "vin": [ { "gen": { "height": 1262363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64c37c96a01e4b90325e8dc4bb2c480a21f984201b053d8976735ae2e7a1caa" } } ], "extra": [ 1, 35, 184, 85, 165, 177, 37, 209, 161, 177, 224, 102, 66, 83, 22, 60, 156, 245, 78, 20, 120, 7, 168, 103, 169, 221, 19, 140, 62, 8, 173, 239, 251, 2, 17, 0, 0, 0, 1, 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