Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e23a717dcb1ffaa5550ca083059274a109fda3a0e4c95a2c33299585d53eca

Tx prefix hash: 2e5ed1c928113c13c94a6a5febc9cb463a6810d7f460ebe5fdfbd1cbb4d3b809
Tx public key: 0a3eb6a598861b676cd2a0b4e427bac09bbba6773664030c8e28c841372c8265
Timestamp: 1711162477 Timestamp [UCT]: 2024-03-23 02:54:37 Age [y:d:h:m:s]: 00:361:08:44:20
Block: 984305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258370 RingCT/type: yes/0
Extra: 010a3eb6a598861b676cd2a0b4e427bac09bbba6773664030c8e28c841372c82650211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e256d1cf04a381c0b3f5d4a9a9b6c114c77557ba4ade724cb9997cfaecee93f 0.600000000000 1444474 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": 984315, "vin": [ { "gen": { "height": 984305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e256d1cf04a381c0b3f5d4a9a9b6c114c77557ba4ade724cb9997cfaecee93f" } } ], "extra": [ 1, 10, 62, 182, 165, 152, 134, 27, 103, 108, 210, 160, 180, 228, 39, 186, 192, 155, 187, 166, 119, 54, 100, 3, 12, 142, 40, 200, 65, 55, 44, 130, 101, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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