Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6333cb3d1a529041bba3bc007094e367c1ccfd40ca637931c4d043ce8c6f5acd

Tx prefix hash: 3a11b1b846a64b943b18e0f70fe5bade4bccd3fdc2f0bed9951bd3ef315df80b
Tx public key: b8567582a208d4ca4b92a56b6d66e5c4d62b0bb52ee1a439764fabcccc2ce829
Timestamp: 1583077981 Timestamp [UCT]: 2020-03-01 15:53:01 Age [y:d:h:m:s]: 04:301:14:40:17
Block: 74526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109591 RingCT/type: yes/0
Extra: 01b8567582a208d4ca4b92a56b6d66e5c4d62b0bb52ee1a439764fabcccc2ce82902110000030b56c366d3000000000000000000

1 output(s) for total of 347.588358669000 dcy

stealth address amount amount idx
00: 8df82117c6510bacbeb417f50309400e05d97df4e215c422f72c0686cf722eb7 347.588358669000 137910 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": 74536, "vin": [ { "gen": { "height": 74526 } } ], "vout": [ { "amount": 347588358669, "target": { "key": "8df82117c6510bacbeb417f50309400e05d97df4e215c422f72c0686cf722eb7" } } ], "extra": [ 1, 184, 86, 117, 130, 162, 8, 212, 202, 75, 146, 165, 107, 109, 102, 229, 196, 214, 43, 11, 181, 46, 225, 164, 57, 118, 79, 171, 204, 204, 44, 232, 41, 2, 17, 0, 0, 3, 11, 86, 195, 102, 211, 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