Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67918984977bb84b772761bb3be10be7078ea68fc980d3063ec761b4f8dc1c8a

Tx prefix hash: bf7f445e6ed378f4cc4695e07263404471fb9a42ce127d1dc64c8129c744c84e
Tx public key: 7c177c44fa1626a2f30808c8fed16b514f4f8f7570a5de34a4073e6d910093e8
Timestamp: 1713065463 Timestamp [UCT]: 2024-04-14 03:31:03 Age [y:d:h:m:s]: 00:317:16:54:00
Block: 1000045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227130 RingCT/type: yes/0
Extra: 017c177c44fa1626a2f30808c8fed16b514f4f8f7570a5de34a4073e6d910093e802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e333c05f011e9f55e698da360f985b1df5eec25f08d4fa18a3badbd2b0073afd 0.600000000000 1460535 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": 1000055, "vin": [ { "gen": { "height": 1000045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e333c05f011e9f55e698da360f985b1df5eec25f08d4fa18a3badbd2b0073afd" } } ], "extra": [ 1, 124, 23, 124, 68, 250, 22, 38, 162, 243, 8, 8, 200, 254, 209, 107, 81, 79, 79, 143, 117, 112, 165, 222, 52, 164, 7, 62, 109, 145, 0, 147, 232, 2, 17, 0, 0, 0, 2, 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