Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2a647cd3b877d86b7b1ab9d91689255ba558637cfe82c536249ef399313375

Tx prefix hash: b5c037387a0b6c8c85a74d9dc8b65b9ed473d949ec96887d7996c57cb55c4221
Tx public key: bf7676809bc10bf4c41c3556b6ca00b66fd0c85412bef46e44201ee21f99e82d
Timestamp: 1754320271 Timestamp [UCT]: 2025-08-04 15:11:11 Age [y:d:h:m:s]: 00:105:07:52:43
Block: 1340178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74226 RingCT/type: yes/0
Extra: 01bf7676809bc10bf4c41c3556b6ca00b66fd0c85412bef46e44201ee21f99e82d021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e1b52f1d626f020fbf8f2956f849d51d733d6a1c815568be5e08e4c6f5a2998 0.600000000000 1827995 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": 1340188, "vin": [ { "gen": { "height": 1340178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e1b52f1d626f020fbf8f2956f849d51d733d6a1c815568be5e08e4c6f5a2998" } } ], "extra": [ 1, 191, 118, 118, 128, 155, 193, 11, 244, 196, 28, 53, 86, 182, 202, 0, 182, 111, 208, 200, 84, 18, 190, 244, 110, 68, 32, 30, 226, 31, 153, 232, 45, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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