Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00773d0135f8e10e764c7e39dfe544b414923892afbf8e91f06f1b580840c2b8

Tx prefix hash: e7e6cb1a001548f22d160474e84f9f898c365390ce47835692b3a0b857b01ad9
Tx public key: a30c1ac43e06d846c2b78377a071dc3794b75c29e809afb593172c4fa40cc708
Timestamp: 1696705358 Timestamp [UCT]: 2023-10-07 19:02:38 Age [y:d:h:m:s]: 01:091:07:15:02
Block: 864632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326516 RingCT/type: yes/0
Extra: 01a30c1ac43e06d846c2b78377a071dc3794b75c29e809afb593172c4fa40cc708021100000001bfa22221000000000000000000

1 output(s) for total of 0.837751653000 dcy

stealth address amount amount idx
00: 81b5a39fd373e75dd35fa1940653f06d95b87b13e11a44816bcb4a11dce89d3d 0.837751653000 1319152 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": 864642, "vin": [ { "gen": { "height": 864632 } } ], "vout": [ { "amount": 837751653, "target": { "key": "81b5a39fd373e75dd35fa1940653f06d95b87b13e11a44816bcb4a11dce89d3d" } } ], "extra": [ 1, 163, 12, 26, 196, 62, 6, 216, 70, 194, 183, 131, 119, 160, 113, 220, 55, 148, 183, 92, 41, 232, 9, 175, 181, 147, 23, 44, 79, 164, 12, 199, 8, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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