Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e087b0db0e0dbd39bf343d28571add9cc8d74547f2f886dace14a2a185bd1e

Tx prefix hash: 5420d7e22983b1746c0b1c86a754dbf46217db45a623fe33a4e97bb20b90e313
Tx public key: e55bf6f7a24efe5c74efe6082bca87c06f28d886c247a6f7847dc2ce1323c5a2
Timestamp: 1728996992 Timestamp [UCT]: 2024-10-15 12:56:32 Age [y:d:h:m:s]: 00:194:11:19:36
Block: 1132151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138784 RingCT/type: yes/0
Extra: 01e55bf6f7a24efe5c74efe6082bca87c06f28d886c247a6f7847dc2ce1323c5a202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bc240697202700870346b763d77c3081ce5b9d18c134e2de07ca03959c50871 0.600000000000 1615064 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": 1132161, "vin": [ { "gen": { "height": 1132151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bc240697202700870346b763d77c3081ce5b9d18c134e2de07ca03959c50871" } } ], "extra": [ 1, 229, 91, 246, 247, 162, 78, 254, 92, 116, 239, 230, 8, 43, 202, 135, 192, 111, 40, 216, 134, 194, 71, 166, 247, 132, 125, 194, 206, 19, 35, 197, 162, 2, 17, 0, 0, 0, 1, 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