Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1beb7f75effd7f506ab64bada5074573124049f020331aa66f8994ba325648b

Tx prefix hash: 60f37296f5bd3962f8d5508adb298a11c69d4e7ff2bac096353c7a99ce61040b
Tx public key: 4d1cc6bf0ea8d1a10a2d74d7e069d411d9dfd6618f8a1ad3582fb17c3139a0fa
Timestamp: 1706640588 Timestamp [UCT]: 2024-01-30 18:49:48 Age [y:d:h:m:s]: 01:286:07:36:00
Block: 946776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463436 RingCT/type: yes/0
Extra: 014d1cc6bf0ea8d1a10a2d74d7e069d411d9dfd6618f8a1ad3582fb17c3139a0fa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b20dfe039c25c49b13bfd1329153b566d5262b8d6f6339af6e20cc4d32792130 0.600000000000 1405116 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": 946786, "vin": [ { "gen": { "height": 946776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b20dfe039c25c49b13bfd1329153b566d5262b8d6f6339af6e20cc4d32792130" } } ], "extra": [ 1, 77, 28, 198, 191, 14, 168, 209, 161, 10, 45, 116, 215, 224, 105, 212, 17, 217, 223, 214, 97, 143, 138, 26, 211, 88, 47, 177, 124, 49, 57, 160, 250, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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