Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7ffdd3d0ebc68c11e057fab6b6f04c9e3c8f36917e00cda9f6cf11fca7c9970

Tx prefix hash: b2db9fef99434ec090c0f195a6d2e5d1e5f14f05b8fc1187af79680924319024
Tx public key: 72267206c2bb0891a162e052ceafa6ea51db3922f56a6d0a3ceec6aef277f07b
Timestamp: 1702268195 Timestamp [UCT]: 2023-12-11 04:16:35 Age [y:d:h:m:s]: 02:049:05:20:59
Block: 910548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554830 RingCT/type: yes/0
Extra: 0172267206c2bb0891a162e052ceafa6ea51db3922f56a6d0a3ceec6aef277f07b021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7c96466a51ef2de3def61fbbb91b6e3e74d3e7f231fbfdc2840de9263737a39 0.600000000000 1367709 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": 910558, "vin": [ { "gen": { "height": 910548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c96466a51ef2de3def61fbbb91b6e3e74d3e7f231fbfdc2840de9263737a39" } } ], "extra": [ 1, 114, 38, 114, 6, 194, 187, 8, 145, 161, 98, 224, 82, 206, 175, 166, 234, 81, 219, 57, 34, 245, 106, 109, 10, 60, 238, 198, 174, 242, 119, 240, 123, 2, 17, 0, 0, 0, 1, 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