Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831070b65051b384e82719b8cde909cc8c64446cf8bc49a56d01245fcf42d92b

Tx prefix hash: 04ffb1a1c9e5e33bab97760c2e969c552e221017fc0ab6c34ae5bb2255ebf7e0
Tx public key: 3145171d25d43c875f9178d0815f5445d0b16b5fe7e3c1cc6a202415f01f33e2
Timestamp: 1694910658 Timestamp [UCT]: 2023-09-17 00:30:58 Age [y:d:h:m:s]: 01:229:14:22:58
Block: 849739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425196 RingCT/type: yes/0
Extra: 013145171d25d43c875f9178d0815f5445d0b16b5fe7e3c1cc6a202415f01f33e2021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.938559925000 dcy

stealth address amount amount idx
00: 3a1f4af6c9352852376bac85bffdd6fb2ee5e7fa9ce5fe7ed9a93eb30fde8861 0.938559925000 1303417 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": 849749, "vin": [ { "gen": { "height": 849739 } } ], "vout": [ { "amount": 938559925, "target": { "key": "3a1f4af6c9352852376bac85bffdd6fb2ee5e7fa9ce5fe7ed9a93eb30fde8861" } } ], "extra": [ 1, 49, 69, 23, 29, 37, 212, 60, 135, 95, 145, 120, 208, 129, 95, 84, 69, 208, 177, 107, 95, 231, 227, 193, 204, 106, 32, 36, 21, 240, 31, 51, 226, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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