Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f1246c6108965be62de29938486edce6c406847e9c6aa58474cdda1e3b395cf

Tx prefix hash: cf4429998f8902a41ee9dfd2a50c9c9aa0421de629df277414e32637c48075ff
Tx public key: 9976fa4a5dcce586ceaf56e751cbb449f73e53e14ca8ccb5a3d0ba29de976cf5
Timestamp: 1702909643 Timestamp [UCT]: 2023-12-18 14:27:23 Age [y:d:h:m:s]: 01:178:20:04:18
Block: 915871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388910 RingCT/type: yes/0
Extra: 019976fa4a5dcce586ceaf56e751cbb449f73e53e14ca8ccb5a3d0ba29de976cf502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575c04e0133b1e418d2e095edac225029d54e3a5e8b5b9d80890305f7ff0825e 0.600000000000 1373305 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": 915881, "vin": [ { "gen": { "height": 915871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575c04e0133b1e418d2e095edac225029d54e3a5e8b5b9d80890305f7ff0825e" } } ], "extra": [ 1, 153, 118, 250, 74, 93, 204, 229, 134, 206, 175, 86, 231, 81, 203, 180, 73, 247, 62, 83, 225, 76, 168, 204, 181, 163, 208, 186, 41, 222, 151, 108, 245, 2, 17, 0, 0, 0, 4, 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