Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1dc77f54e6f54bb11decd4b420d39f71129353a052b70f08de4a4a2627c122

Tx prefix hash: ed21c5df0a0b7a2fe6695bc83897da26b2ea065eb5a117d0cc54e2646c69e96a
Tx public key: a4cea9db7ae3596ecbb8df7992ef3a3b47d5fcc295a0de472cd166470155951d
Timestamp: 1721634589 Timestamp [UCT]: 2024-07-22 07:49:49 Age [y:d:h:m:s]: 00:252:10:44:36
Block: 1071100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180345 RingCT/type: yes/0
Extra: 01a4cea9db7ae3596ecbb8df7992ef3a3b47d5fcc295a0de472cd166470155951d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62bdad8f06e9b7a68f45b1da6ba6d92285cacc405d30d2e93736c94315420bb2 0.600000000000 1543199 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": 1071110, "vin": [ { "gen": { "height": 1071100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62bdad8f06e9b7a68f45b1da6ba6d92285cacc405d30d2e93736c94315420bb2" } } ], "extra": [ 1, 164, 206, 169, 219, 122, 227, 89, 110, 203, 184, 223, 121, 146, 239, 58, 59, 71, 213, 252, 194, 149, 160, 222, 71, 44, 209, 102, 71, 1, 85, 149, 29, 2, 17, 0, 0, 0, 7, 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