Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2a38321fdfad715d474c10a70b301c01a04537bc5f37a3f1471fdfcd00b4ab

Tx prefix hash: f87d367e480bec62b441aaf1ab7f08db45d13c63b16392f25c43cf32d87f4364
Tx public key: 6885a4d4bffc076a0341ff2e1d738ca7b4f39abaac77517065ffb614d7dc86a6
Timestamp: 1724998171 Timestamp [UCT]: 2024-08-30 06:09:31 Age [y:d:h:m:s]: 00:260:00:06:24
Block: 1098991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185709 RingCT/type: yes/0
Extra: 016885a4d4bffc076a0341ff2e1d738ca7b4f39abaac77517065ffb614d7dc86a6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e22ef150c88b0aa95d5af713cb0bd1335135437e7dc65fb39143cd0192aadf3d 0.600000000000 1574898 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": 1099001, "vin": [ { "gen": { "height": 1098991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e22ef150c88b0aa95d5af713cb0bd1335135437e7dc65fb39143cd0192aadf3d" } } ], "extra": [ 1, 104, 133, 164, 212, 191, 252, 7, 106, 3, 65, 255, 46, 29, 115, 140, 167, 180, 243, 154, 186, 172, 119, 81, 112, 101, 255, 182, 20, 215, 220, 134, 166, 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