Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fc97078b66bf108e979a8b09f8e464d9c5daa51f307e3554cc5a07491c8249

Tx prefix hash: e038c850329156cbf901dd94c27403f83da76e2c08fe8e1b136944189b31c6dc
Tx public key: 0c215bc0db75adbd9fc5c0d20b0a4fc8ec9a7c5ab5a3bc3db6302173b8a1105d
Timestamp: 1711291174 Timestamp [UCT]: 2024-03-24 14:39:34 Age [y:d:h:m:s]: 00:296:12:14:16
Block: 985373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212228 RingCT/type: yes/0
Extra: 010c215bc0db75adbd9fc5c0d20b0a4fc8ec9a7c5ab5a3bc3db6302173b8a1105d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 742051bfcb7daccde3ee616fe118579d3ac62685c7039ca3586479ced1b3ecec 0.600000000000 1445582 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": 985383, "vin": [ { "gen": { "height": 985373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "742051bfcb7daccde3ee616fe118579d3ac62685c7039ca3586479ced1b3ecec" } } ], "extra": [ 1, 12, 33, 91, 192, 219, 117, 173, 189, 159, 197, 192, 210, 11, 10, 79, 200, 236, 154, 124, 90, 181, 163, 188, 61, 182, 48, 33, 115, 184, 161, 16, 93, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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