Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d7c0814dfbbf8a1f9734e834f009708d5483bb11785ccaade128046ee8b886d

Tx prefix hash: a62e06c59920f687ab6dbd7ee7a64786fe6bd3a3865c35b517bc1ae0419a3dfc
Tx public key: d3f7086830856a4de98bc964cacce411ae38edb3ccca4fdaaa3eae9895bf37f5
Timestamp: 1698785288 Timestamp [UCT]: 2023-10-31 20:48:08 Age [y:d:h:m:s]: 01:140:22:30:51
Block: 881882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361737 RingCT/type: yes/0
Extra: 01d3f7086830856a4de98bc964cacce411ae38edb3ccca4fdaaa3eae9895bf37f5021100000002faf35c9c000000000000000000

1 output(s) for total of 0.734444288000 dcy

stealth address amount amount idx
00: c0629ed8cabb34e2953908af706fbbb2d26b64d30bd1f814796db0bf356e6587 0.734444288000 1337504 of 0

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": 881892, "vin": [ { "gen": { "height": 881882 } } ], "vout": [ { "amount": 734444288, "target": { "key": "c0629ed8cabb34e2953908af706fbbb2d26b64d30bd1f814796db0bf356e6587" } } ], "extra": [ 1, 211, 247, 8, 104, 48, 133, 106, 77, 233, 139, 201, 100, 202, 204, 228, 17, 174, 56, 237, 179, 204, 202, 79, 218, 170, 62, 174, 152, 149, 191, 55, 245, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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