Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ccc035249bd880b7aa33f380d9ca10df6fc403431bcbd78c78c420cf3a1cd7a

Tx prefix hash: 46ead01e7bbdd1040066c9f110789297f159bb47a7a06416671bf69e3dcd068e
Tx public key: 803a187ac16de7932b4cf0c2f6aa1d1c36dcbefdf52d4458a1ba571114aec250
Timestamp: 1729767531 Timestamp [UCT]: 2024-10-24 10:58:51 Age [y:d:h:m:s]: 00:090:04:45:35
Block: 1138495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64452 RingCT/type: yes/0
Extra: 01803a187ac16de7932b4cf0c2f6aa1d1c36dcbefdf52d4458a1ba571114aec2500211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c54b7db87612a214aa90c9d973f33d2a4dfe3fc117f75ddec271130a5b057a8 0.600000000000 1622176 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": 1138505, "vin": [ { "gen": { "height": 1138495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c54b7db87612a214aa90c9d973f33d2a4dfe3fc117f75ddec271130a5b057a8" } } ], "extra": [ 1, 128, 58, 24, 122, 193, 109, 231, 147, 43, 76, 240, 194, 246, 170, 29, 28, 54, 220, 190, 253, 245, 45, 68, 88, 161, 186, 87, 17, 20, 174, 194, 80, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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