Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92328dd81aa1e2542af7cbb9f18692dffdd81896a8c041f62823b7469260ff7a

Tx prefix hash: 33cb4eaf41ba8f778af820c86dfd3fcd7c20d93465d35043929559b831570fdb
Tx public key: ebe415081ed818e80da037ec92e09fe4c7411f1d05635c93860710fc904a0065
Timestamp: 1713933626 Timestamp [UCT]: 2024-04-24 04:40:26 Age [y:d:h:m:s]: 00:307:01:36:29
Block: 1007261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219479 RingCT/type: yes/0
Extra: 01ebe415081ed818e80da037ec92e09fe4c7411f1d05635c93860710fc904a00650211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfaf21ea00b4f2ed0e327c664e91e3fe1ff78e45a086e323b7f3c281263aed45 0.600000000000 1468543 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": 1007271, "vin": [ { "gen": { "height": 1007261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfaf21ea00b4f2ed0e327c664e91e3fe1ff78e45a086e323b7f3c281263aed45" } } ], "extra": [ 1, 235, 228, 21, 8, 30, 216, 24, 232, 13, 160, 55, 236, 146, 224, 159, 228, 199, 65, 31, 29, 5, 99, 92, 147, 134, 7, 16, 252, 144, 74, 0, 101, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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