Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3191d3818ce1114d83b6396d4e257d7014c053d7fbb192f7623901eec8e655f0

Tx prefix hash: 055348b82cce6ab3af8cab6f7db80cf49cf2c21d5b4856f7e19a977e9a9e10b5
Tx public key: 2ee2434c224da9e63e48f1a3261607329fcaf80d2164b79af5b1ca17ca613512
Timestamp: 1724227422 Timestamp [UCT]: 2024-08-21 08:03:42 Age [y:d:h:m:s]: 00:230:07:07:06
Block: 1092615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164449 RingCT/type: yes/0
Extra: 012ee2434c224da9e63e48f1a3261607329fcaf80d2164b79af5b1ca17ca613512021100000001e914dd15000000000000000000

1 output(s) for total of 0.605760000000 dcy

stealth address amount amount idx
00: 99c21b7a1e38c86fa6416e84910895b83a2ce8523cff4a36e9c56583d7bd4440 0.605760000000 1567394 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": 1092625, "vin": [ { "gen": { "height": 1092615 } } ], "vout": [ { "amount": 605760000, "target": { "key": "99c21b7a1e38c86fa6416e84910895b83a2ce8523cff4a36e9c56583d7bd4440" } } ], "extra": [ 1, 46, 226, 67, 76, 34, 77, 169, 230, 62, 72, 241, 163, 38, 22, 7, 50, 159, 202, 248, 13, 33, 100, 183, 154, 245, 177, 202, 23, 202, 97, 53, 18, 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