Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e16fd9e011e2db20160557c754481bed5dd86835252cf41b55226d83345206

Tx prefix hash: ead2ad21aa0fdc65e7b761b4d653e5dda99cd0f5fb0df21c28996694cb7eb83b
Tx public key: 6ae66090cb4ada965d09a54482e9f29a3975e8af071bed81fb4a51089c99e5ef
Timestamp: 1682924299 Timestamp [UCT]: 2023-05-01 06:58:19 Age [y:d:h:m:s]: 01:345:20:47:27
Block: 750438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508434 RingCT/type: yes/0
Extra: 016ae66090cb4ada965d09a54482e9f29a3975e8af071bed81fb4a51089c99e5ef0211000000027e406890000000000000000000

1 output(s) for total of 2.002108396000 dcy

stealth address amount amount idx
00: 0c986388a18fbdf697aeb34bcd5e0691d5dc7f867232fb1a3d5bb315c8fd6a38 2.002108396000 1198509 of 0

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": 750448, "vin": [ { "gen": { "height": 750438 } } ], "vout": [ { "amount": 2002108396, "target": { "key": "0c986388a18fbdf697aeb34bcd5e0691d5dc7f867232fb1a3d5bb315c8fd6a38" } } ], "extra": [ 1, 106, 230, 96, 144, 203, 74, 218, 150, 93, 9, 165, 68, 130, 233, 242, 154, 57, 117, 232, 175, 7, 27, 237, 129, 251, 74, 81, 8, 156, 153, 229, 239, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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