Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e3bc1b3f8469b6b52c0f5c08ad0c54173b65d8c22ed47d449da7e305320a173

Tx prefix hash: 21e246a3ecbe7c7f2a80c78f5433948eeafd100d1f0e861656534d480b35d39a
Tx public key: a45aeb72d359997d7d43fbdc4a109bdccd2b8966ed3c979628b794ddb1dd9026
Timestamp: 1578948729 Timestamp [UCT]: 2020-01-13 20:52:09 Age [y:d:h:m:s]: 05:296:09:04:54
Block: 44958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359631 RingCT/type: yes/0
Extra: 01a45aeb72d359997d7d43fbdc4a109bdccd2b8966ed3c979628b794ddb1dd90260211000000078a2ee0d9000000000000000000

1 output(s) for total of 435.548300445000 dcy

stealth address amount amount idx
00: fbba951fbdd1d46dc73c288c29e28f92433cff267714eedcadaa37fdcac6eb88 435.548300445000 81990 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": 44968, "vin": [ { "gen": { "height": 44958 } } ], "vout": [ { "amount": 435548300445, "target": { "key": "fbba951fbdd1d46dc73c288c29e28f92433cff267714eedcadaa37fdcac6eb88" } } ], "extra": [ 1, 164, 90, 235, 114, 211, 89, 153, 125, 125, 67, 251, 220, 74, 16, 155, 220, 205, 43, 137, 102, 237, 60, 151, 150, 40, 183, 148, 221, 177, 221, 144, 38, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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