Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf21f56449c13fb574a8faafacb26d453fc416320ea6ad92b8bc1626366f82f

Tx prefix hash: 3cfcaa18bf6f2657d95a21eae43a9d15b66bfdd0f225f958856241f0f3ca28db
Tx public key: 37f7573d1465c96b6105cdcb42e5e003e673d5065d03aa62cbe45c816a7875c8
Timestamp: 1582058637 Timestamp [UCT]: 2020-02-18 20:43:57 Age [y:d:h:m:s]: 05:015:10:53:31
Block: 67734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164072 RingCT/type: yes/0
Extra: 0137f7573d1465c96b6105cdcb42e5e003e673d5065d03aa62cbe45c816a7875c80211000000104943cd9f000000000000000000

1 output(s) for total of 366.108235672000 dcy

stealth address amount amount idx
00: 33bb5d5104718ea28363710d091b6c72fc89ace3176b25f04235e978660a32d4 366.108235672000 124743 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": 67744, "vin": [ { "gen": { "height": 67734 } } ], "vout": [ { "amount": 366108235672, "target": { "key": "33bb5d5104718ea28363710d091b6c72fc89ace3176b25f04235e978660a32d4" } } ], "extra": [ 1, 55, 247, 87, 61, 20, 101, 201, 107, 97, 5, 205, 203, 66, 229, 224, 3, 230, 115, 213, 6, 93, 3, 170, 98, 203, 228, 92, 129, 106, 120, 117, 200, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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