Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4112ea9debd2e1b0641773818baf52bad147f4b8c4e0a1c8e641a464cbe16c2

Tx prefix hash: 76cd22862d104ee9d97c27e0b1e072972859c24cd77baf091dc69521136b1c6d
Tx public key: e496e6b9e076765ac3fb03fc3d4ccecbf5e55922d296e848ca8c378ce228a7a1
Timestamp: 1741100314 Timestamp [UCT]: 2025-03-04 14:58:34 Age [y:d:h:m:s]: 00:329:22:44:12
Block: 1232028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233477 RingCT/type: yes/0
Extra: 01e496e6b9e076765ac3fb03fc3d4ccecbf5e55922d296e848ca8c378ce228a7a10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1daae3e6f4fc314f982eb0a2f1773a5a48e3743dfc4b8ba2849c34a009d48237 0.600000000000 1718939 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": 1232038, "vin": [ { "gen": { "height": 1232028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1daae3e6f4fc314f982eb0a2f1773a5a48e3743dfc4b8ba2849c34a009d48237" } } ], "extra": [ 1, 228, 150, 230, 185, 224, 118, 118, 90, 195, 251, 3, 252, 61, 76, 206, 203, 245, 229, 89, 34, 210, 150, 232, 72, 202, 140, 55, 140, 226, 40, 167, 161, 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