Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901ac0dad90818553a34b366e18ec34d18a4debf52ab15ebf733d8da9c06a030

Tx prefix hash: c8d3f186da1492cf9d8d14b386333f263b76a0af435def4b52aa4e07322106d6
Tx public key: c191fb15559337e4f700ea2dc5228edcb1fd81b1170b2a632018e763d83cec59
Timestamp: 1578173618 Timestamp [UCT]: 2020-01-04 21:33:38 Age [y:d:h:m:s]: 05:060:15:02:38
Block: 38806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193149 RingCT/type: yes/0
Extra: 01c191fb15559337e4f700ea2dc5228edcb1fd81b1170b2a632018e763d83cec5902110000005e2264afe6000000000000000000

1 output(s) for total of 456.478641931000 dcy

stealth address amount amount idx
00: 8e50373b02bbfad2abcbd6c96299e7c1fd8c244ad8fbe52b2b211d6d5ae284eb 456.478641931000 66432 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": 38816, "vin": [ { "gen": { "height": 38806 } } ], "vout": [ { "amount": 456478641931, "target": { "key": "8e50373b02bbfad2abcbd6c96299e7c1fd8c244ad8fbe52b2b211d6d5ae284eb" } } ], "extra": [ 1, 193, 145, 251, 21, 85, 147, 55, 228, 247, 0, 234, 45, 197, 34, 142, 220, 177, 253, 129, 177, 23, 11, 42, 99, 32, 24, 231, 99, 216, 60, 236, 89, 2, 17, 0, 0, 0, 94, 34, 100, 175, 230, 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