Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b4e762b9acaed206b49caba73f375a655ead3e80c7bbf3800ce0654ba44a46

Tx prefix hash: de0557962eb6c0580fb164c3cd0ae9a776ff947cb2d670da0ca826bc30e62bff
Tx public key: fedf8acb2ec47077f0e8e44b0fa3d5f87610fb295e0cf8cdf5245d3426573fff
Timestamp: 1674670849 Timestamp [UCT]: 2023-01-25 18:20:49 Age [y:d:h:m:s]: 02:081:21:27:44
Block: 682630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580179 RingCT/type: yes/0
Extra: 01fedf8acb2ec47077f0e8e44b0fa3d5f87610fb295e0cf8cdf5245d3426573fff0211000000035029cbac000000000000000000

1 output(s) for total of 3.358639378000 dcy

stealth address amount amount idx
00: c21b44453fbba04d63050c161c4c4473cb28dff324fcdd2bea2ee499e54df981 3.358639378000 1124767 of 0

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": 682640, "vin": [ { "gen": { "height": 682630 } } ], "vout": [ { "amount": 3358639378, "target": { "key": "c21b44453fbba04d63050c161c4c4473cb28dff324fcdd2bea2ee499e54df981" } } ], "extra": [ 1, 254, 223, 138, 203, 46, 196, 112, 119, 240, 232, 228, 75, 15, 163, 213, 248, 118, 16, 251, 41, 94, 12, 248, 205, 245, 36, 93, 52, 38, 87, 63, 255, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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