Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9becce306439f16c1eb6bc3b42ec376e2782278e8f8f7b5117099ea5cc4cebb

Tx prefix hash: bfbea1d072d2056d42e11636f5e3a0d67a3e9ff309b0902f8c4ff8eb45a9806e
Tx public key: d19b30ec40ef929e7fd485576e7b45450308b49b263041169f61ce14fcef66fa
Timestamp: 1751731498 Timestamp [UCT]: 2025-07-05 16:04:58 Age [y:d:h:m:s]: 00:126:15:32:52
Block: 1319344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88874 RingCT/type: yes/0
Extra: 01d19b30ec40ef929e7fd485576e7b45450308b49b263041169f61ce14fcef66fa0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f72f6b351160e27d3ee7840405bdf22bce130c6da30f9d4df89dac86de32eb6f 0.600000000000 1807035 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": 1319354, "vin": [ { "gen": { "height": 1319344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f72f6b351160e27d3ee7840405bdf22bce130c6da30f9d4df89dac86de32eb6f" } } ], "extra": [ 1, 209, 155, 48, 236, 64, 239, 146, 158, 127, 212, 133, 87, 110, 123, 69, 69, 3, 8, 180, 155, 38, 48, 65, 22, 159, 97, 206, 20, 252, 239, 102, 250, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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