Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ec20f6841fb18ab00d7eac9de0bfa918c76ebe7ed47a1a767d4db0e4f39d38

Tx prefix hash: c0926e9204297d50251cd53b023c8fca95ea32bad12336f92c5dc23d5a29e21d
Tx public key: 8b6cc08c489d9d4adbf998ee87a80d10af02b5ab7bdbe6a024082ad65fb8cad5
Timestamp: 1711178911 Timestamp [UCT]: 2024-03-23 07:28:31 Age [y:d:h:m:s]: 01:026:22:58:37
Block: 984452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280213 RingCT/type: yes/0
Extra: 018b6cc08c489d9d4adbf998ee87a80d10af02b5ab7bdbe6a024082ad65fb8cad50211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5c46ac5218df83c3458fd2f222e9b2406f472d98bce763e56735ad5e38c7d8a 0.600000000000 1444623 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": 984462, "vin": [ { "gen": { "height": 984452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5c46ac5218df83c3458fd2f222e9b2406f472d98bce763e56735ad5e38c7d8a" } } ], "extra": [ 1, 139, 108, 192, 140, 72, 157, 157, 74, 219, 249, 152, 238, 135, 168, 13, 16, 175, 2, 181, 171, 123, 219, 230, 160, 36, 8, 42, 214, 95, 184, 202, 213, 2, 17, 0, 0, 0, 9, 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