Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bf1a6e3ecb34a23864a975c10392608c948740439e3f4c209885b2cbf70ee44

Tx prefix hash: 826d8c7542101ed4f78c6ee8868ff18f4e1d757e1384e16ae8b57ba57b5e91e0
Tx public key: bdb2336aee5930c93ffd6dda01091facc93e8c8fa324ff6ab4a78ce577fd4b63
Timestamp: 1733125558 Timestamp [UCT]: 2024-12-02 07:45:58 Age [y:d:h:m:s]: 00:119:03:37:15
Block: 1166279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84952 RingCT/type: yes/0
Extra: 01bdb2336aee5930c93ffd6dda01091facc93e8c8fa324ff6ab4a78ce577fd4b63021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc99f8c521cb15b36f1ca0b8c4d2eff04dd47bd964e5f9790817466b847b74a8 0.600000000000 1651956 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": 1166289, "vin": [ { "gen": { "height": 1166279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc99f8c521cb15b36f1ca0b8c4d2eff04dd47bd964e5f9790817466b847b74a8" } } ], "extra": [ 1, 189, 178, 51, 106, 238, 89, 48, 201, 63, 253, 109, 218, 1, 9, 31, 172, 201, 62, 140, 143, 163, 36, 255, 106, 180, 167, 140, 229, 119, 253, 75, 99, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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