Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 881baade1cdb49f5a9d197f4dc13ee92ae732a78a7d0e36fa1a23f5cea3ba93a

Tx prefix hash: 32b22e0dc7fba8992c910fbc4dfe296d316ffb2ecf1c4c835dff825c0ace50d3
Tx public key: 9fbbd72722a3851cbd4349d2f2648c5478e97fa1217a281b09012f1ce6986cc5
Timestamp: 1724298153 Timestamp [UCT]: 2024-08-22 03:42:33 Age [y:d:h:m:s]: 00:236:18:09:47
Block: 1093198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169080 RingCT/type: yes/0
Extra: 019fbbd72722a3851cbd4349d2f2648c5478e97fa1217a281b09012f1ce6986cc5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e868505bc10eac2226e1129df13c741299301af91c708d8172808b6a5f2063ec 0.600000000000 1568093 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": 1093208, "vin": [ { "gen": { "height": 1093198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e868505bc10eac2226e1129df13c741299301af91c708d8172808b6a5f2063ec" } } ], "extra": [ 1, 159, 187, 215, 39, 34, 163, 133, 28, 189, 67, 73, 210, 242, 100, 140, 84, 120, 233, 127, 161, 33, 122, 40, 27, 9, 1, 47, 28, 230, 152, 108, 197, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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