Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5937e843d15ba6f17a090714d336f43d0cd6934a281482549065304ef355b2ec

Tx prefix hash: 84292da924a7988f809d009f1134448b2f43a94cab832c7c3184c4c596af9b49
Tx public key: 3b891ecceed07e56b3815183344b71e6177e7734dff81fc4a2ff655f4d66ae40
Timestamp: 1583851151 Timestamp [UCT]: 2020-03-10 14:39:11 Age [y:d:h:m:s]: 04:359:09:33:43
Block: 79773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151815 RingCT/type: yes/0
Extra: 013b891ecceed07e56b3815183344b71e6177e7734dff81fc4a2ff655f4d66ae40021100000008a08fd034000000000000000000

1 output(s) for total of 333.948675974000 dcy

stealth address amount amount idx
00: b88935610cc9bd0b7fd2d1d2f490216bf77d578e488a67b4e57ead1af442803a 333.948675974000 145973 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": 79783, "vin": [ { "gen": { "height": 79773 } } ], "vout": [ { "amount": 333948675974, "target": { "key": "b88935610cc9bd0b7fd2d1d2f490216bf77d578e488a67b4e57ead1af442803a" } } ], "extra": [ 1, 59, 137, 30, 204, 238, 208, 126, 86, 179, 129, 81, 131, 52, 75, 113, 230, 23, 126, 119, 52, 223, 248, 31, 196, 162, 255, 101, 95, 77, 102, 174, 64, 2, 17, 0, 0, 0, 8, 160, 143, 208, 52, 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