Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e86a92547c8318c35daa42b2ea676b3e97a6f761cbbb88c7d383a534be5f98

Tx prefix hash: a6a8e9f653402f6db56a7c283ea6d34451099b3294f4af0c2028e249c945770b
Tx public key: 6b870263bac2382fbbf7749a63ce36540814af381e8f1ce76250d3c7c7541d04
Timestamp: 1732608530 Timestamp [UCT]: 2024-11-26 08:08:50 Age [y:d:h:m:s]: 00:131:01:20:15
Block: 1161988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93475 RingCT/type: yes/0
Extra: 016b870263bac2382fbbf7749a63ce36540814af381e8f1ce76250d3c7c7541d04021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb52fec22330a0bd8e99ccb3f93a75a6fa365d7b959e40dc7b33f3724212ae61 0.600000000000 1647643 of 15

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": 1161998, "vin": [ { "gen": { "height": 1161988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb52fec22330a0bd8e99ccb3f93a75a6fa365d7b959e40dc7b33f3724212ae61" } } ], "extra": [ 1, 107, 135, 2, 99, 186, 194, 56, 47, 187, 247, 116, 154, 99, 206, 54, 84, 8, 20, 175, 56, 30, 143, 28, 231, 98, 80, 211, 199, 199, 84, 29, 4, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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