Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bd7d33d5c6f5516957f523812ac649e50dd61b8beccb214d7e376a031a15b26

Tx prefix hash: b2c1b66367837f9b8dff1eb08081293f066d4583ea3acdebdf91f241b53c75d0
Tx public key: 2e63065e419eb269dc175d69cbcb1b8ee2a90de6ce6202b83a472845a9b1338d
Timestamp: 1710306173 Timestamp [UCT]: 2024-03-13 05:02:53 Age [y:d:h:m:s]: 01:242:14:44:12
Block: 977201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432097 RingCT/type: yes/0
Extra: 012e63065e419eb269dc175d69cbcb1b8ee2a90de6ce6202b83a472845a9b1338d02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b982807f6eeb9fc81ea35c2de12652f4708222cb9a60ff1de0b7750b1aa61e2b 0.600000000000 1437202 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": 977211, "vin": [ { "gen": { "height": 977201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b982807f6eeb9fc81ea35c2de12652f4708222cb9a60ff1de0b7750b1aa61e2b" } } ], "extra": [ 1, 46, 99, 6, 94, 65, 158, 178, 105, 220, 23, 93, 105, 203, 203, 27, 142, 226, 169, 13, 230, 206, 98, 2, 184, 58, 71, 40, 69, 169, 177, 51, 141, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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