Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4364fa59ef93d1fdd021f07953e49360f73d398f0010b38af4b8a33d0ec741d5

Tx prefix hash: fb726dd6904d753cba8505d858595072a623526a390cc8338ddb6a3e06e6925f
Tx public key: fb6b91a545b2060363fd14172b472a540c2a1aeac400355e302cb51596e3bd8a
Timestamp: 1707117084 Timestamp [UCT]: 2024-02-05 07:11:24 Age [y:d:h:m:s]: 01:060:14:14:53
Block: 950728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304374 RingCT/type: yes/0
Extra: 01fb6b91a545b2060363fd14172b472a540c2a1aeac400355e302cb51596e3bd8a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c716f6cd7647287de0aa358fc1b2e02e591a7ddce4fb0452787a39c8e48fa246 0.600000000000 1409394 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": 950738, "vin": [ { "gen": { "height": 950728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c716f6cd7647287de0aa358fc1b2e02e591a7ddce4fb0452787a39c8e48fa246" } } ], "extra": [ 1, 251, 107, 145, 165, 69, 178, 6, 3, 99, 253, 20, 23, 43, 71, 42, 84, 12, 42, 26, 234, 196, 0, 53, 94, 48, 44, 181, 21, 150, 227, 189, 138, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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