Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ff8c8968f209df82fcabb42ec8bfaa9b84b43431ea3855700bc1520996e736a

Tx prefix hash: 4400a5c00d8f76b36e342bdc405829db852d10535beca87a17fbf67a15932f84
Tx public key: c1f2b87e9facaac0c6f55f1a7bd0bb94db58ca561842461c4c0548820f2aae94
Timestamp: 1697159351 Timestamp [UCT]: 2023-10-13 01:09:11 Age [y:d:h:m:s]: 01:168:14:10:55
Block: 868390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381524 RingCT/type: yes/0
Extra: 01c1f2b87e9facaac0c6f55f1a7bd0bb94db58ca561842461c4c0548820f2aae9402110000000233af99f4000000000000000000

1 output(s) for total of 0.814073230000 dcy

stealth address amount amount idx
00: 222dc6593e0fb67caa5a70df894af9dc3d4248bad6944368ceeae5d78dbb69b9 0.814073230000 1323197 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": 868400, "vin": [ { "gen": { "height": 868390 } } ], "vout": [ { "amount": 814073230, "target": { "key": "222dc6593e0fb67caa5a70df894af9dc3d4248bad6944368ceeae5d78dbb69b9" } } ], "extra": [ 1, 193, 242, 184, 126, 159, 172, 170, 192, 198, 245, 95, 26, 123, 208, 187, 148, 219, 88, 202, 86, 24, 66, 70, 28, 76, 5, 72, 130, 15, 42, 174, 148, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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