Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f96ccb5443958c4db9d6d59957fb0799f5e8fdc704cb024f45aacabce605d7

Tx prefix hash: e8b5a0143d7ac416da629cda5f8465c8f60a68aa8e364fbb64a2d7251b3541ee
Tx public key: 8107a644bf8ba8de913b0cb817b0831c15028d77bef58cba9b672461e8498c9a
Timestamp: 1700655154 Timestamp [UCT]: 2023-11-22 12:12:34 Age [y:d:h:m:s]: 01:185:09:40:10
Block: 897176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393717 RingCT/type: yes/0
Extra: 018107a644bf8ba8de913b0cb817b0831c15028d77bef58cba9b672461e8498c9a02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.653556990000 dcy

stealth address amount amount idx
00: fc7cbffb13611cb0e9f52b28d7007a7f39d7dba4b911f62059916be52a771bbf 0.653556990000 1353541 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": 897186, "vin": [ { "gen": { "height": 897176 } } ], "vout": [ { "amount": 653556990, "target": { "key": "fc7cbffb13611cb0e9f52b28d7007a7f39d7dba4b911f62059916be52a771bbf" } } ], "extra": [ 1, 129, 7, 166, 68, 191, 139, 168, 222, 145, 59, 12, 184, 23, 176, 131, 28, 21, 2, 141, 119, 190, 245, 140, 186, 155, 103, 36, 97, 232, 73, 140, 154, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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