Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de1bc9353f957640ccc40268b635686e3cefa33d0353bd5caaa0f95448f35698

Tx prefix hash: 78b0eb776d7c34d6c7a2f583d13222d63175499f0e6387d58902040122fb6dac
Tx public key: f5d63d24bb5de01dd8cc1037a8148bedcab2426ce245cc0e3967166ae12a0fa6
Timestamp: 1696716959 Timestamp [UCT]: 2023-10-07 22:15:59 Age [y:d:h:m:s]: 01:185:13:40:13
Block: 864734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393665 RingCT/type: yes/0
Extra: 01f5d63d24bb5de01dd8cc1037a8148bedcab2426ce245cc0e3967166ae12a0fa602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.837099967000 dcy

stealth address amount amount idx
00: 7d48c0a14764b13167e5ab023e4dcf1f2b6e20c370f92938c70f3932712dd3c2 0.837099967000 1319254 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": 864744, "vin": [ { "gen": { "height": 864734 } } ], "vout": [ { "amount": 837099967, "target": { "key": "7d48c0a14764b13167e5ab023e4dcf1f2b6e20c370f92938c70f3932712dd3c2" } } ], "extra": [ 1, 245, 214, 61, 36, 187, 93, 224, 29, 216, 204, 16, 55, 168, 20, 139, 237, 202, 178, 66, 108, 226, 69, 204, 14, 57, 103, 22, 106, 225, 42, 15, 166, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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