Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0c69acfeedf93f731058c99edd55d12be0769fd96b7fb7c25b5008ac08fc0e5

Tx prefix hash: 08c05f7d1fac329a90522fd78a21866e11985516d744d6b64dae008a2f7ec26e
Tx public key: 29fc07afbcffc92ca6b919462d197ce1b417a327373e1a9abc8b37bda20e4a86
Timestamp: 1657036022 Timestamp [UCT]: 2022-07-05 15:47:02 Age [y:d:h:m:s]: 03:118:21:55:57
Block: 537265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864697 RingCT/type: yes/0
Extra: 0129fc07afbcffc92ca6b919462d197ce1b417a327373e1a9abc8b37bda20e4a8602110000000a4da16a3a000000000000000000

1 output(s) for total of 10.181650300000 dcy

stealth address amount amount idx
00: 29bcec5397faec8ddce8562ccbe71d7a8590e2517db20d59b458ae66c41f444a 10.181650300000 967134 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": 537275, "vin": [ { "gen": { "height": 537265 } } ], "vout": [ { "amount": 10181650300, "target": { "key": "29bcec5397faec8ddce8562ccbe71d7a8590e2517db20d59b458ae66c41f444a" } } ], "extra": [ 1, 41, 252, 7, 175, 188, 255, 201, 44, 166, 185, 25, 70, 45, 25, 124, 225, 180, 23, 163, 39, 55, 62, 26, 154, 188, 139, 55, 189, 162, 14, 74, 134, 2, 17, 0, 0, 0, 10, 77, 161, 106, 58, 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