Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c262670f0b9c0e76dcd0709295ddb4052a094c53dd7c9100b96685afbbc7cfc0

Tx prefix hash: 3ecd812e3ce74bac56b5b36a2b9fb1d7e3eddbc62649809d6b7b7e3bbfd96832
Tx public key: 682b684c4cec5b1bf7094451153f1974de3a133d373ea58deb0df8a689b974d0
Timestamp: 1712496283 Timestamp [UCT]: 2024-04-07 13:24:43 Age [y:d:h:m:s]: 00:221:17:00:51
Block: 995317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158735 RingCT/type: yes/0
Extra: 01682b684c4cec5b1bf7094451153f1974de3a133d373ea58deb0df8a689b974d00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4cc6b14fc88396a3935438d99ddf54bd8e30d374ea3a00b2eecf2454ffe4bb3 0.600000000000 1455723 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": 995327, "vin": [ { "gen": { "height": 995317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4cc6b14fc88396a3935438d99ddf54bd8e30d374ea3a00b2eecf2454ffe4bb3" } } ], "extra": [ 1, 104, 43, 104, 76, 76, 236, 91, 27, 247, 9, 68, 81, 21, 63, 25, 116, 222, 58, 19, 61, 55, 62, 165, 141, 235, 13, 248, 166, 137, 185, 116, 208, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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