Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d6068433bff78f4dd36fb778555a5c6cc068e0a2e29a367fa280577e35f88e

Tx prefix hash: 82424f7949267eeb0b77843adefbb1048f20f94a609422ec3ecd052a684aea56
Tx public key: de56577e417654da6b7f74f6ed08b95054fcc019d8d8eb0966ad63904e29ad1d
Timestamp: 1578191350 Timestamp [UCT]: 2020-01-05 02:29:10 Age [y:d:h:m:s]: 04:360:00:23:21
Block: 38918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146523 RingCT/type: yes/0
Extra: 01de56577e417654da6b7f74f6ed08b95054fcc019d8d8eb0966ad63904e29ad1d021100000001d81c26c0000000000000000000

1 output(s) for total of 456.088749614000 dcy

stealth address amount amount idx
00: 867bc3ac2f0f9e3b09573e17496e31be611f5efde812957399655b02da8c3570 456.088749614000 66716 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": 38928, "vin": [ { "gen": { "height": 38918 } } ], "vout": [ { "amount": 456088749614, "target": { "key": "867bc3ac2f0f9e3b09573e17496e31be611f5efde812957399655b02da8c3570" } } ], "extra": [ 1, 222, 86, 87, 126, 65, 118, 84, 218, 107, 127, 116, 246, 237, 8, 185, 80, 84, 252, 192, 25, 216, 216, 235, 9, 102, 173, 99, 144, 78, 41, 173, 29, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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