Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fba01aaa24034ca15b24331a6b247656e8dae9fbc1a96405b3286cd5cbfc163

Tx prefix hash: 9ee5f8f13e6edea2d4443e638f6e867a2e7172a9d24c7575ff2a3e068e72ef43
Tx public key: 7b89b9d8418773a55a781cff3fef69e828d462bc489e6af44836e1d86ba09bda
Timestamp: 1708818271 Timestamp [UCT]: 2024-02-24 23:44:31 Age [y:d:h:m:s]: 00:347:07:21:56
Block: 964856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248333 RingCT/type: yes/0
Extra: 017b89b9d8418773a55a781cff3fef69e828d462bc489e6af44836e1d86ba09bda0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01f5cd9bc4d4998156f9c77699092915e3e52feb1d26c0a149ed8c7925455a6a 0.600000000000 1424599 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": 964866, "vin": [ { "gen": { "height": 964856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01f5cd9bc4d4998156f9c77699092915e3e52feb1d26c0a149ed8c7925455a6a" } } ], "extra": [ 1, 123, 137, 185, 216, 65, 135, 115, 165, 90, 120, 28, 255, 63, 239, 105, 232, 40, 212, 98, 188, 72, 158, 106, 244, 72, 54, 225, 216, 107, 160, 155, 218, 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