Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 891da190c37d74fbc5b5797c7bf8b1d91ae2b760344db169d8b3ab49af35b7ef

Tx prefix hash: 0fe9ea5407ef5385faa9f7625d12bdc3d7cc58e9a4589db8bc0c1ff5d62bbb29
Tx public key: 73c6c0db5877ee2ff3f24626ec7cf3f373cbbda6256843621f3ec6b907ef80e8
Timestamp: 1713348845 Timestamp [UCT]: 2024-04-17 10:14:05 Age [y:d:h:m:s]: 01:057:23:58:36
Block: 1002413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302364 RingCT/type: yes/0
Extra: 0173c6c0db5877ee2ff3f24626ec7cf3f373cbbda6256843621f3ec6b907ef80e802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dabcae6f143ac55953664d68471b02514dc2ba718d5b8e4319e9f23794f00147 0.600000000000 1462929 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": 1002423, "vin": [ { "gen": { "height": 1002413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dabcae6f143ac55953664d68471b02514dc2ba718d5b8e4319e9f23794f00147" } } ], "extra": [ 1, 115, 198, 192, 219, 88, 119, 238, 47, 243, 242, 70, 38, 236, 124, 243, 243, 115, 203, 189, 166, 37, 104, 67, 98, 31, 62, 198, 185, 7, 239, 128, 232, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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