Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62910c8523785f951b417fd4455ac8953ae2146fb5aeebaf434f8bfe50dd041d

Tx prefix hash: de9c265507b30eb3dab3d047be770cd8b730f94bf6011e96456075b699d168f5
Tx public key: eca98f584588d16b1793ad08b6fe417e11cfd6444f3206fe404da3d63f8ee079
Timestamp: 1725476322 Timestamp [UCT]: 2024-09-04 18:58:42 Age [y:d:h:m:s]: 00:259:00:00:20
Block: 1102958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184997 RingCT/type: yes/0
Extra: 01eca98f584588d16b1793ad08b6fe417e11cfd6444f3206fe404da3d63f8ee079021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a56cd4b66a9b2c5d38a8fd75803890a8c10d2d0bd57647cf21cfd006d2f2c6bd 0.600000000000 1579603 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": 1102968, "vin": [ { "gen": { "height": 1102958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a56cd4b66a9b2c5d38a8fd75803890a8c10d2d0bd57647cf21cfd006d2f2c6bd" } } ], "extra": [ 1, 236, 169, 143, 88, 69, 136, 209, 107, 23, 147, 173, 8, 182, 254, 65, 126, 17, 207, 214, 68, 79, 50, 6, 254, 64, 77, 163, 214, 63, 142, 224, 121, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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