Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6058fe0ab69cdfab488dbbccda181f5c9b84ee1dca4b764a2a811441e960b22d

Tx prefix hash: 08671883b7463566fc4f8b5ce44e4b9be3bfc23bfeb295d6fdb6dcb4cff0a0f1
Tx public key: a3e1f3b6c68da0621cc6a3d570a84d7900a2cbe6bd47bf6f034e46136b9f4ac4
Timestamp: 1725941267 Timestamp [UCT]: 2024-09-10 04:07:47 Age [y:d:h:m:s]: 00:123:15:37:22
Block: 1106809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88421 RingCT/type: yes/0
Extra: 01a3e1f3b6c68da0621cc6a3d570a84d7900a2cbe6bd47bf6f034e46136b9f4ac402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 432d26d8af4ef553eaec78f0bb5291e63166e03ba0dac1ce3fa9b79eb11b6603 0.600000000000 1584410 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": 1106819, "vin": [ { "gen": { "height": 1106809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "432d26d8af4ef553eaec78f0bb5291e63166e03ba0dac1ce3fa9b79eb11b6603" } } ], "extra": [ 1, 163, 225, 243, 182, 198, 141, 160, 98, 28, 198, 163, 213, 112, 168, 77, 121, 0, 162, 203, 230, 189, 71, 191, 111, 3, 78, 70, 19, 107, 159, 74, 196, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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