Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 179f4599e2e29e5ca0121c8499eb2ee70d484b9acc889f30c35459a8ac31122d

Tx prefix hash: 3333d5eb1c6a992bd63dae263d7f5db36ecf8579b0d5c3f2c2b0663477fb31b5
Tx public key: c864a1f1a01a7332fdd1e3249a68c30790740c7c7e9ea93cb08aa29f2beef2f8
Timestamp: 1726587357 Timestamp [UCT]: 2024-09-17 15:35:57 Age [y:d:h:m:s]: 01:054:15:28:24
Block: 1112162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297469 RingCT/type: yes/0
Extra: 01c864a1f1a01a7332fdd1e3249a68c30790740c7c7e9ea93cb08aa29f2beef2f802110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31d0f7fe3c61404a8882bac3f2a8b017955b4b30512396b23c4512adfd8234cb 0.600000000000 1591387 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": 1112172, "vin": [ { "gen": { "height": 1112162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31d0f7fe3c61404a8882bac3f2a8b017955b4b30512396b23c4512adfd8234cb" } } ], "extra": [ 1, 200, 100, 161, 241, 160, 26, 115, 50, 253, 209, 227, 36, 154, 104, 195, 7, 144, 116, 12, 124, 126, 158, 169, 60, 176, 138, 162, 159, 43, 238, 242, 248, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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