Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fadc0d3761cbc9c3ce2dd9a54839945c42e6e6a4ff2505dbf176f73d88d1bdf

Tx prefix hash: 5f6291068c51645f17588adda8738a41ddb2dfb215bff9e05ec753981698befe
Tx public key: cf42b3f6b372a87e86f3a9505005f0fbcda5a776d55009899be1137688621e9f
Timestamp: 1583234351 Timestamp [UCT]: 2020-03-03 11:19:11 Age [y:d:h:m:s]: 04:253:18:48:28
Block: 75260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075931 RingCT/type: yes/0
Extra: 01cf42b3f6b372a87e86f3a9505005f0fbcda5a776d55009899be1137688621e9f02110000026f56c366d3000000000000000000

1 output(s) for total of 345.647304942000 dcy

stealth address amount amount idx
00: ff10bdc97cd34a72dfabb39db97feef6f6bac2e76d934ba1fe4e6fad85a5f548 345.647304942000 139181 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": 75270, "vin": [ { "gen": { "height": 75260 } } ], "vout": [ { "amount": 345647304942, "target": { "key": "ff10bdc97cd34a72dfabb39db97feef6f6bac2e76d934ba1fe4e6fad85a5f548" } } ], "extra": [ 1, 207, 66, 179, 246, 179, 114, 168, 126, 134, 243, 169, 80, 80, 5, 240, 251, 205, 165, 167, 118, 213, 80, 9, 137, 155, 225, 19, 118, 136, 98, 30, 159, 2, 17, 0, 0, 2, 111, 86, 195, 102, 211, 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