Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c14d29b6e039179f7379297f1767ed2749c48479bbe047c6b2b58f1933f3674

Tx prefix hash: 1b034d9e4d0765c5c7632b4c09e8c392207782340a6473ebb355abf6f69f38a6
Tx public key: df3e7f0d3baf3a8151f17e81ec4f69ecd7a12b0ee54e3a15b0bb6a4ff170afcf
Timestamp: 1727348897 Timestamp [UCT]: 2024-09-26 11:08:17 Age [y:d:h:m:s]: 01:057:00:25:23
Block: 1118483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299154 RingCT/type: yes/0
Extra: 01df3e7f0d3baf3a8151f17e81ec4f69ecd7a12b0ee54e3a15b0bb6a4ff170afcf02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c7c5128f7bf5ecb2f41006308a41d287b12c962afb2fe77377e7e1b2307d6e4 0.600000000000 1599692 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": 1118493, "vin": [ { "gen": { "height": 1118483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c7c5128f7bf5ecb2f41006308a41d287b12c962afb2fe77377e7e1b2307d6e4" } } ], "extra": [ 1, 223, 62, 127, 13, 59, 175, 58, 129, 81, 241, 126, 129, 236, 79, 105, 236, 215, 161, 43, 14, 229, 78, 58, 21, 176, 187, 106, 79, 241, 112, 175, 207, 2, 17, 0, 0, 0, 14, 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