Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36728689f4ab129f4c7be74f372bba22e8ecc5376f0cf9455bff2ec3b7c43b8

Tx prefix hash: d285c7189699bc48df17f7ec828b4ff192179840c705a4e0105a6c0b11754dc7
Tx public key: 3dd0514ffea8c00e97410a4a0c83d3addb4d21a3698ea8315d624fc57b03c142
Timestamp: 1706004744 Timestamp [UCT]: 2024-01-23 10:12:24 Age [y:d:h:m:s]: 01:288:08:57:33
Block: 941505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464898 RingCT/type: yes/0
Extra: 013dd0514ffea8c00e97410a4a0c83d3addb4d21a3698ea8315d624fc57b03c14202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e530636c86cef6918c15f716dcf61ae92375ab4dd4d69826744f8b10e6fac243 0.600000000000 1399655 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": 941515, "vin": [ { "gen": { "height": 941505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e530636c86cef6918c15f716dcf61ae92375ab4dd4d69826744f8b10e6fac243" } } ], "extra": [ 1, 61, 208, 81, 79, 254, 168, 192, 14, 151, 65, 10, 74, 12, 131, 211, 173, 219, 77, 33, 163, 105, 142, 168, 49, 93, 98, 79, 197, 123, 3, 193, 66, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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