Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1629b308977f63fbb679b7cb7f1acd2d978e4cc39ac264d7c32d69903cba9470

Tx prefix hash: 1df15e2070cd9470658776de54bd7058dcfcaabe8c1b2915d60e6d0b583f62a3
Tx public key: bdd76d7ccd0ef66b98f41e1143048b633280f41f58bafaac2112c6b51f4e315c
Timestamp: 1759521201 Timestamp [UCT]: 2025-10-03 19:53:21 Age [y:d:h:m:s]: 00:095:16:12:23
Block: 1382082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68524 RingCT/type: yes/0
Extra: 01bdd76d7ccd0ef66b98f41e1143048b633280f41f58bafaac2112c6b51f4e315c02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d1174ec1a58218bc6e7a48d27b9f2705ab9b2652ab553a81c639b7a20ad6f5 0.600000000000 1870217 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": 1382092, "vin": [ { "gen": { "height": 1382082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d1174ec1a58218bc6e7a48d27b9f2705ab9b2652ab553a81c639b7a20ad6f5" } } ], "extra": [ 1, 189, 215, 109, 124, 205, 14, 246, 107, 152, 244, 30, 17, 67, 4, 139, 99, 50, 128, 244, 31, 88, 186, 250, 172, 33, 18, 198, 181, 31, 78, 49, 92, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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