Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5257ac4f6f515aaaa0c0ba4e11fc99fe017c7c25ff66b02ba5feaf6e2c3fdad8

Tx prefix hash: 0d559abb7dd92db56f28ac9b705626cebd0e791e5221068222b24075e0020e03
Tx public key: b9a75aa57d06a6f859891082d81d4dec8648e99a9e69e9b5295636d9b96ff3a7
Timestamp: 1708133209 Timestamp [UCT]: 2024-02-17 01:26:49 Age [y:d:h:m:s]: 01:039:08:01:41
Block: 959168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289123 RingCT/type: yes/0
Extra: 01b9a75aa57d06a6f859891082d81d4dec8648e99a9e69e9b5295636d9b96ff3a702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63752c89da4b8a7e87f1ea54b86533f281104b7099138091076a91529a71494e 0.600000000000 1418699 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": 959178, "vin": [ { "gen": { "height": 959168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63752c89da4b8a7e87f1ea54b86533f281104b7099138091076a91529a71494e" } } ], "extra": [ 1, 185, 167, 90, 165, 125, 6, 166, 248, 89, 137, 16, 130, 216, 29, 77, 236, 134, 72, 233, 154, 158, 105, 233, 181, 41, 86, 54, 217, 185, 111, 243, 167, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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