Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1b0ea9b4fde5e796e16fcb6898a55611d5cc2379a2c0961b284ce65134304bd

Tx prefix hash: dd82a2dfc162aa8b1cd7db35b4a1466c6f97081daf71b4f6c89879a5c431c51e
Tx public key: 28e5ea3c3ddc531291dfe39ebede5433b9f00315aa0b63484b567d0b15248e5b
Timestamp: 1700214676 Timestamp [UCT]: 2023-11-17 09:51:16 Age [y:d:h:m:s]: 01:173:06:29:17
Block: 893530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385019 RingCT/type: yes/0
Extra: 0128e5ea3c3ddc531291dfe39ebede5433b9f00315aa0b63484b567d0b15248e5b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.671992121000 dcy

stealth address amount amount idx
00: c32b6e4fb3ab4c2575b66e5dd151f25ac87159c499192a4e3e079face11f8d58 0.671992121000 1349701 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": 893540, "vin": [ { "gen": { "height": 893530 } } ], "vout": [ { "amount": 671992121, "target": { "key": "c32b6e4fb3ab4c2575b66e5dd151f25ac87159c499192a4e3e079face11f8d58" } } ], "extra": [ 1, 40, 229, 234, 60, 61, 220, 83, 18, 145, 223, 227, 158, 190, 222, 84, 51, 185, 240, 3, 21, 170, 11, 99, 72, 75, 86, 125, 11, 21, 36, 142, 91, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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