Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53a0b830cf10afe6b0d4fa3cc17170fe7f8464dbc5df2a0889a9177dc738e75

Tx prefix hash: b5134c5fc4315dc9fe8501ba255804d48058306c83e03a5d31717ce11253ac63
Tx public key: a5662d29f8d56d67dff16aa70e05c6595a05a79a6f251188cc9e699720a739f6
Timestamp: 1718968102 Timestamp [UCT]: 2024-06-21 11:08:22 Age [y:d:h:m:s]: 00:344:21:16:23
Block: 1048982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246527 RingCT/type: yes/0
Extra: 01a5662d29f8d56d67dff16aa70e05c6595a05a79a6f251188cc9e699720a739f602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 039088892fcafbe179bdf07e2cbd92d6694a770d23c4a7ac5db0aee50a81cb10 0.600000000000 1519079 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": 1048992, "vin": [ { "gen": { "height": 1048982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "039088892fcafbe179bdf07e2cbd92d6694a770d23c4a7ac5db0aee50a81cb10" } } ], "extra": [ 1, 165, 102, 45, 41, 248, 213, 109, 103, 223, 241, 106, 167, 14, 5, 198, 89, 90, 5, 167, 154, 111, 37, 17, 136, 204, 158, 105, 151, 32, 167, 57, 246, 2, 17, 0, 0, 0, 4, 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