Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b92cfb5caa5667fd6ecc3ee8e19f1d05b7f2e38c59a8f4cd1304824f05c9b53

Tx prefix hash: 82d837501d4c0ccdd183c5dd6cf00737565928baed2017fa396a436374507c69
Tx public key: 019e6b8ab43f2c4190a8ecc9cea3aa7de31a67528b705ad836dd1010df3521e9
Timestamp: 1730858734 Timestamp [UCT]: 2024-11-06 02:05:34 Age [y:d:h:m:s]: 00:148:11:38:11
Block: 1147486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105961 RingCT/type: yes/0
Extra: 01019e6b8ab43f2c4190a8ecc9cea3aa7de31a67528b705ad836dd1010df3521e9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c90bba3fe5a0c4af28068b9fb534380d2f6cff9ccb3143910fa51094d6d5d221 0.600000000000 1632183 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": 1147496, "vin": [ { "gen": { "height": 1147486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c90bba3fe5a0c4af28068b9fb534380d2f6cff9ccb3143910fa51094d6d5d221" } } ], "extra": [ 1, 1, 158, 107, 138, 180, 63, 44, 65, 144, 168, 236, 201, 206, 163, 170, 125, 227, 26, 103, 82, 139, 112, 90, 216, 54, 221, 16, 16, 223, 53, 33, 233, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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