Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8eac42318417f4e8632d2e46490e737f65c2b7cfcaf0d813690f5ba73893019

Tx prefix hash: 66afb1d4e861b9dbc0d1f3eaba66a0ec72af4d1e14fdf5597d07e8b0faf20e5c
Tx public key: c6788cdbc28c3431c0ff2fc8d58c4648900a636f837a3e84e778e1b855d4be29
Timestamp: 1703876579 Timestamp [UCT]: 2023-12-29 19:02:59 Age [y:d:h:m:s]: 01:100:11:26:52
Block: 923882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332912 RingCT/type: yes/0
Extra: 01c6788cdbc28c3431c0ff2fc8d58c4648900a636f837a3e84e778e1b855d4be290211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 590e36879f17f02ea67c90a43c54d7edab32a37902dd56db12e3a857ff84fddc 0.600000000000 1381620 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": 923892, "vin": [ { "gen": { "height": 923882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "590e36879f17f02ea67c90a43c54d7edab32a37902dd56db12e3a857ff84fddc" } } ], "extra": [ 1, 198, 120, 140, 219, 194, 140, 52, 49, 192, 255, 47, 200, 213, 140, 70, 72, 144, 10, 99, 111, 131, 122, 62, 132, 231, 120, 225, 184, 85, 212, 190, 41, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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