Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ea0d47fd7648f016aec73b31cbe1e7036472abd7184adb1ae5b1993d9a8de99

Tx prefix hash: 3ebfc4b3c53e714c1f05714211b98ab31c924cfd5f9d9faa4369a4071d5dbe39
Tx public key: 59dd0e75d82faf17f1b1a5ce5ba0234154bc98ac22ea5e6da281b144f22b555e
Timestamp: 1578938086 Timestamp [UCT]: 2020-01-13 17:54:46 Age [y:d:h:m:s]: 04:321:21:47:22
Block: 44851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119508 RingCT/type: yes/0
Extra: 0159dd0e75d82faf17f1b1a5ce5ba0234154bc98ac22ea5e6da281b144f22b555e0211000000074ac5aa02000000000000000000

1 output(s) for total of 435.904004741000 dcy

stealth address amount amount idx
00: 68a992352c98d430f6f29a0ec16a7b3669c8da310154e2d79c94fd40f19ea3ba 435.904004741000 81750 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": 44861, "vin": [ { "gen": { "height": 44851 } } ], "vout": [ { "amount": 435904004741, "target": { "key": "68a992352c98d430f6f29a0ec16a7b3669c8da310154e2d79c94fd40f19ea3ba" } } ], "extra": [ 1, 89, 221, 14, 117, 216, 47, 175, 23, 241, 177, 165, 206, 91, 160, 35, 65, 84, 188, 152, 172, 34, 234, 94, 109, 162, 129, 177, 68, 242, 43, 85, 94, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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