Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0675ad3825aea3d0c6563f4d6f24ce3b7b2d97efde6afe1da80a1fb935c522b6

Tx prefix hash: 55dd259c683c157cd62a1eb60fd0adaac50ed6851a2644c5c43845f1cc950975
Tx public key: 70d053847332d09419af998e20d66e1842bfaeee2577fe651acac92b1a66e948
Timestamp: 1705285021 Timestamp [UCT]: 2024-01-15 02:17:01 Age [y:d:h:m:s]: 01:117:16:13:16
Block: 935531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345240 RingCT/type: yes/0
Extra: 0170d053847332d09419af998e20d66e1842bfaeee2577fe651acac92b1a66e94802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44e39ac0ec45851a1effa5fdbc828e4dfa26693a729bccb9df3e94cd6ecc581f 0.600000000000 1393547 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": 935541, "vin": [ { "gen": { "height": 935531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44e39ac0ec45851a1effa5fdbc828e4dfa26693a729bccb9df3e94cd6ecc581f" } } ], "extra": [ 1, 112, 208, 83, 132, 115, 50, 208, 148, 25, 175, 153, 142, 32, 214, 110, 24, 66, 191, 174, 238, 37, 119, 254, 101, 26, 202, 201, 43, 26, 102, 233, 72, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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