Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14b856e5ac23822f5f5a59c0695540d94baaded0f04afb7cec8913407590c8f7

Tx prefix hash: e29afcaf164039393b1c2d80fa8e3f5ee7dd1dd4dcef860c6c351eda63edd534
Tx public key: abe75dc696cb2e11caca726ad932351b6f0d4a3257131b85e3161ff89108a87e
Timestamp: 1702714956 Timestamp [UCT]: 2023-12-16 08:22:36 Age [y:d:h:m:s]: 01:036:16:34:39
Block: 914254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287540 RingCT/type: yes/0
Extra: 01abe75dc696cb2e11caca726ad932351b6f0d4a3257131b85e3161ff89108a87e02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed8abea309d5d55387ec257f8059d6969b7d6b36fd0699516af50fb80165d065 0.600000000000 1371540 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": 914264, "vin": [ { "gen": { "height": 914254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed8abea309d5d55387ec257f8059d6969b7d6b36fd0699516af50fb80165d065" } } ], "extra": [ 1, 171, 231, 93, 198, 150, 203, 46, 17, 202, 202, 114, 106, 217, 50, 53, 27, 111, 13, 74, 50, 87, 19, 27, 133, 227, 22, 31, 248, 145, 8, 168, 126, 2, 17, 0, 0, 0, 2, 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