Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6e831cc6424d81a1cd74ec23bb7222078e317ba72240dc8682a378aa2d81aa

Tx prefix hash: 97ca5f40d01581df26f2f5f132574b2c5cdc91b3bd155346ec4c831f388ec91e
Tx public key: d24a1e9ee6b3e33e7747cef769e523c0a621ccef80e5028e3107d7ec3b7fce6e
Timestamp: 1730733658 Timestamp [UCT]: 2024-11-04 15:20:58 Age [y:d:h:m:s]: 00:130:03:56:45
Block: 1146451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92876 RingCT/type: yes/0
Extra: 01d24a1e9ee6b3e33e7747cef769e523c0a621ccef80e5028e3107d7ec3b7fce6e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a23c4995059459f9e8cd17dc0eb3a560b45255d6240eaa38c96f6a2b62be058 0.600000000000 1631096 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": 1146461, "vin": [ { "gen": { "height": 1146451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a23c4995059459f9e8cd17dc0eb3a560b45255d6240eaa38c96f6a2b62be058" } } ], "extra": [ 1, 210, 74, 30, 158, 230, 179, 227, 62, 119, 71, 206, 247, 105, 229, 35, 192, 166, 33, 204, 239, 128, 229, 2, 142, 49, 7, 215, 236, 59, 127, 206, 110, 2, 17, 0, 0, 0, 1, 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