Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36fcaaf8d3e69979896a5927e75b916cec3b09e33666549a1bb9644db647b863

Tx prefix hash: e37b8cdd293316c4c1f02b9d2a6c71a05725f9fe20a7821c176129d9b39073d6
Tx public key: e953d0dfa87d721b97b5a30ac9cd79cdd5bdcd1abe4d4fe6791e240dfa184aef
Timestamp: 1643957994 Timestamp [UCT]: 2022-02-04 06:59:54 Age [y:d:h:m:s]: 02:301:05:24:06
Block: 431869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733832 RingCT/type: yes/0
Extra: 01e953d0dfa87d721b97b5a30ac9cd79cdd5bdcd1abe4d4fe6791e240dfa184aef02110000000bc9067537000000000000000000

1 output(s) for total of 22.755539079000 dcy

stealth address amount amount idx
00: 0bb8659c37992efb7de8ee4d8c50ddbf7635e449af92bd50846d913cc7093cd8 22.755539079000 842220 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": 431879, "vin": [ { "gen": { "height": 431869 } } ], "vout": [ { "amount": 22755539079, "target": { "key": "0bb8659c37992efb7de8ee4d8c50ddbf7635e449af92bd50846d913cc7093cd8" } } ], "extra": [ 1, 233, 83, 208, 223, 168, 125, 114, 27, 151, 181, 163, 10, 201, 205, 121, 205, 213, 189, 205, 26, 190, 77, 79, 230, 121, 30, 36, 13, 250, 24, 74, 239, 2, 17, 0, 0, 0, 11, 201, 6, 117, 55, 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