Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e989a1439f08a2014d519ec39b4e4881b7f105f73c3db7cb36ec547b3090a732

Tx prefix hash: 630b08e2da7f5ba7e44899293fcc369b6d08193ce1e86783c30625a1dbe4631c
Tx public key: 0c4539fdd58a712fc78e504d83b98d9eab3084eed16be571a95de37a16a076a0
Timestamp: 1728109303 Timestamp [UCT]: 2024-10-05 06:21:43 Age [y:d:h:m:s]: 01:035:05:53:23
Block: 1124780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283577 RingCT/type: yes/0
Extra: 010c4539fdd58a712fc78e504d83b98d9eab3084eed16be571a95de37a16a076a0021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 500a1d6a8e7095900ae05b52671f8d8a3d578be3af01ce53c89271785d4cd4f6 0.600000000000 1607449 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": 1124790, "vin": [ { "gen": { "height": 1124780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "500a1d6a8e7095900ae05b52671f8d8a3d578be3af01ce53c89271785d4cd4f6" } } ], "extra": [ 1, 12, 69, 57, 253, 213, 138, 113, 47, 199, 142, 80, 77, 131, 185, 141, 158, 171, 48, 132, 238, 209, 107, 229, 113, 169, 93, 227, 122, 22, 160, 118, 160, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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