Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0231fdfeba7faf114fbc29df9f7bc9a363dd804c3f4f939e9c17087290092e

Tx prefix hash: 730435d7bc74daeb6c25b13c82bce6830aa2b607e32e65349ac4660c8cb56c92
Tx public key: 008307dd50b773e4bc5cda2ec281b9f5e6bf4cefce919eee56e2d46851965754
Timestamp: 1720930016 Timestamp [UCT]: 2024-07-14 04:06:56 Age [y:d:h:m:s]: 00:221:07:45:17
Block: 1065279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158054 RingCT/type: yes/0
Extra: 01008307dd50b773e4bc5cda2ec281b9f5e6bf4cefce919eee56e2d46851965754021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d6b679302c78e236570bc49baefeef6eb7a1a4210c5fc725eb3b32f40795185 0.600000000000 1535824 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": 1065289, "vin": [ { "gen": { "height": 1065279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d6b679302c78e236570bc49baefeef6eb7a1a4210c5fc725eb3b32f40795185" } } ], "extra": [ 1, 0, 131, 7, 221, 80, 183, 115, 228, 188, 92, 218, 46, 194, 129, 185, 245, 230, 191, 76, 239, 206, 145, 158, 238, 86, 226, 212, 104, 81, 150, 87, 84, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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