Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24385659a545d7f9285c5195e99853b43a7e0671e9f69096df8622c8540552a3

Tx prefix hash: 4ead93d5f3c9d3cbec3014536673130a65df8e79db42eee350277e501e8a7609
Tx public key: 4eec56f1ab4acbb89a3a374defb9f3ef9412cc8ca8f5f5458289b48921c7f731
Timestamp: 1702248509 Timestamp [UCT]: 2023-12-10 22:48:29 Age [y:d:h:m:s]: 01:120:23:51:35
Block: 910386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347615 RingCT/type: yes/0
Extra: 014eec56f1ab4acbb89a3a374defb9f3ef9412cc8ca8f5f5458289b48921c7f73102110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c02e9681a533cf703820bdd240433f3ed4c3ca06aef4e9d3039db446aa06b02 0.600000000000 1367537 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": 910396, "vin": [ { "gen": { "height": 910386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c02e9681a533cf703820bdd240433f3ed4c3ca06aef4e9d3039db446aa06b02" } } ], "extra": [ 1, 78, 236, 86, 241, 171, 74, 203, 184, 154, 58, 55, 77, 239, 185, 243, 239, 148, 18, 204, 140, 168, 245, 245, 69, 130, 137, 180, 137, 33, 199, 247, 49, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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